Skip to content

legacy-support-devel: Update to latest master - v20250924. #29460

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Sep 25, 2025
Merged

legacy-support-devel: Update to latest master - v20250924. #29460

merged 1 commit into from
Sep 25, 2025

Conversation

fhgwright
Copy link
Contributor

Notable changes since last -devel:

  • Updates SDK version handling for SDK 26.

Due to the strictness of the version detection, this update is required for successful builds with SDK 26. But since legacy-support doesn't offer any enhancements for OS versions later than 10.15, this is only a problem for clients that unncesessarily use it for later OS versions.

Also switches github.tarball_from to archive for the -devel version, after verifying that this works correctly (earlier attempts didn't). The release version is left unchanged for now.

TESTED:
Tested both normal and -devel versions -/+universal on 10.4-10.5 ppc, 10.4-10.5 ppc64, 10.4-10.6 ppc (i386 Rosetta), 10.4-10.6 i386, 10.4-12.x x86_64, and 11.x-26.x arm64.
Builds and passes all tests on all tested platforms, except for the aforementioned problem building the release version for OS 26.

Description

Type(s)
  • bugfix
  • enhancement
  • security fix
Tested on
Mac OS X 10.4.11 8S165, ppc, Xcode 2.5 8M2558
Mac OS X 10.4.11 8S165, ppc64, Xcode 2.5 8M2558
Mac OS X 10.4.11 8S2167, i386, Xcode 2.5 8M2558
Mac OS X 10.4.11 8S2167, x86_64, Xcode 2.5 8M2558
Mac OS X 10.4.11 8S2167, ppc (i386 Rosetta), Xcode 2.5 8M2558
Mac OS X 10.5.8 9L31a, ppc, Xcode 3.1.4 9M2809
Mac OS X 10.5.8 9L31a, ppc64, Xcode 3.1.4 9M2809
Mac OS X 10.5.8 9L31a, i386, Xcode 3.1.4 9M2809
Mac OS X 10.5.8 9L31a, x86_64, Xcode 3.1.4 9M2809
Mac OS X 10.5.8 9L31a, ppc (i386 Rosetta), Xcode 3.1.4 9M2809
Mac OS X 10.6.8 10K549, i386, Xcode 3.2.6 10M2518
Mac OS X 10.6.8 10K549, x86_64, Xcode 3.2.6 10M2518
Mac OS X 10.6.8 10K549, ppc (i386 Rosetta), Xcode 3.2.6 10M2518
Mac OS X 10.7.5 11G63, x86_64, Xcode 4.6.3 4H1503
OS X 10.8.5 12F2560, x86_64, Xcode 5.1.1 5B1008
OS X 10.9.5 13F1911, x86_64, Xcode 6.2 6C131e
OS X 10.10.5 14F2511, x86_64, Xcode 7.2 7C68
OS X 10.11.6 15G22010, x86_64, Xcode 8.1 8B62
macOS 10.12.6 16G2136, x86_64, Xcode 9.2 9C40b
macOS 10.13.6 17G14042, x86_64, Xcode 10.1 10B61
macOS 10.14.6 18G9323, x86_64, Xcode 11.3.1 11C505
macOS 10.15.7 19H15, x86_64, Xcode 12.4 12D4e
macOS 11.7.10 20G1427, x86_64, Xcode 13.2.1 13C100
macOS 11.7.10 20G1427, arm64, Xcode 13.2.1 13C100
macOS 12.7.6 21H1320, x86_64, Xcode 14.2 14C18
macOS 12.7.6 21H1320, arm64, Xcode 14.2 14C18
macOS 13.7.8 22H730, arm64, Xcode 15.2 15C500b
macOS 14.8 23J21, arm64, Xcode 16.2 16C5032a
macOS 15.7 24G222, arm64, Xcode 26.0 17A324
macOS 26.0 25A354, arm64, Xcode 26.0.1 17A400
Verification

Have you

  • followed our Commit Message Guidelines?
  • squashed and minimized your commits?
  • checked that there aren't other open pull requests for the same change?
  • [N/A] referenced existing tickets on Trac with full URL in commit message?
  • checked your Portfile with port lint?
  • tried existing tests with sudo port test?
  • tried a full install with sudo port -vst install?
  • tested basic functionality of all binary files?
  • checked that the Portfile's most important variants haven't been broken?

@fhgwright
legacy-support-devel: Update to latest master - v20250924.
a2ed9ec 
Notable changes since last -devel:

- Updates SDK version handling for SDK 26.

Due to the strictness of the version detection, this update is
required for successful builds with SDK 26.  But since
`legacy-support` doesn't offer any enhancements for OS versions later
than 10.15, this is only a problem for clients that unncesessarily use
it for later OS versions.

Also switches `github.tarball_from` to `archive` for the -devel
version, after verifying that this works correctly (earlier attempts
didn't).  The release version is left unchanged for now.

TESTED:
Tested both normal and -devel versions -/+universal on 10.4-10.5 ppc,
10.4-10.5 ppc64, 10.4-10.6 ppc (i386 Rosetta), 10.4-10.6 i386,
10.4-12.x x86_64, and 11.x-26.x arm64.
Builds and passes all tests on all tested platforms, except for the
aforementioned problem building the release version for OS 26.
@macportsbot
Copy link

Notifying maintainers:
@mascguy for port legacy-support.

@fhgwright
Copy link
Contributor Author

@mascguy
I'd forgotten about the strictness of the SDK check until I was testing this, though (as noted) it's fairly unlikely to be a problem in practice. Nevertheless, it would probably be a good idea to turn this into a release fairly soon to avoid any trouble. In view of the limited nature of the changes, I don't think it needs the usual full week of soak time. If nobody complains by the weekend, we should probably make it 1.5.2.

I also see that the CI test failed on macos-15, which seems to be a fetch failure. This is most likely a transient, but AFAIK I don't have permission to initiate a retry, other than by pushing a dummy change.

During local testing, I did get a nonrecurring timeout on the distfile fetch by the 10.14 VM, so maybe GitHub is heavily loaded right now.

@mascguy
Copy link
Member

mascguy commented Sep 25, 2025

I also see that the CI test failed on macos-15, which seems to be a fetch failure. This is most likely a transient, but AFAIK I don't have permission to initiate a retry, other than by pushing a dummy change.

I just reran the failed job, and it succeeded this time. So all is good now.

@mascguy mascguy merged commit 977305a into macports:master Sep 25, 2025
5 of 6 checks passed
@fhgwright
Copy link
Contributor Author

@mascguy

I also see that the CI test failed on macos-15, which seems to be a fetch failure. This is most likely a transient, but AFAIK I don't have permission to initiate a retry, other than by pushing a dummy change.

I just reran the failed job, and it succeeded this time. So all is good now.

Thanks. It's also clear that a fetch failure on macos-15 but not macos-13 or macos-14 isn't a fault in the port itself.

@fhgwright fhgwright deleted the legacy-support branch September 26, 2025 01:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@mascguy mascguy mascguy approved these changes

Assignees

@mascguy mascguy

Labels
maintainer: open Affects an openmaintainer port maintainer type: update
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@fhgwright @macportsbot @mascguy